action-allowlist-review: bump 1Password/load-secrets-action from 5.0.0 to 5.0.1 in /.github/actions/for-dependabot-triggered-reviews - #1195
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
added
the
dependencies
dependabot
Bot
added
the
github_actions
Bumps [1Password/load-secrets-action](https://github.com/1password/load-secrets-action) from 5.0.0 to 5.0.1. - [Release notes](https://github.com/1password/load-secrets-action/releases) - [Commits](1Password/load-secrets-action@e544b78...70062d7) --- updated-dependencies: - dependency-name: 1Password/load-secrets-action dependency-version: 5.0.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/dot-github/actions/for-dependabot-triggered-reviews/1Password/load-secrets-action-5.0.1
branch
from
August 27, 2026 18:08
017e476 to
378bcfc
Compare
This was referenced Aug 27, 2026
dfoulks1
pushed a commit
that referenced
this pull request
Sep 1, 2026
The in-tree binary check only knew how to verify a binary against GitHub release provenance - a SLSA attestation or a SHA256SUMS asset. A bundler- copied dependency asset has neither and never will: 1Password/load-secrets- action's dist/core_bg.wasm is ncc output copied from @1password/sdk-core, pinned by sha512 integrity in package-lock.json, so PR #1195 hard-failed on a binary whose provenance chain is npm's rather than the action's. Delete those binaries from the output directory before the rebuild, as the minified JS already is, and credit any that come back byte-identical. That is the same guarantee the JS rebuild check gives. A fully-reproduced action now skips the release lookups entirely; everything else is unchanged. Generated-by: Claude Code (Opus 5)
dfoulks1
pushed a commit
that referenced
this pull request
Sep 1, 2026
…apes Triaging #1167, #1171, #1196 and #1195 turned up two gap kinds the case-E table did not describe - executable non-JS sources missing from the source diff, and an in-tree binary whose provenance is npm's rather than a GitHub release - plus the reading-the-CI-log shortcut that avoids a local Docker rebuild. Generated-by: Claude Code (Opus 5)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps 1Password/load-secrets-action from 5.0.0 to 5.0.1.
Release notes
Sourced from 1Password/load-secrets-action's releases.
Commits
70062d7Merge pull request #190 from 1Password/release/v5.0.16f5bd0ePrepare Release 5.0.1846abe0Merge pull request #187 from 1Password/jill/bump-to-stable-sdk557708fBump sdk type2d8a25cMerge pull request #182 from 1Password/chore/GHA-211518-stepsecurity-remediation631992cApply GitHub Actions security best practices